-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(mypy): fix mypy errors for src/sentry/api/serializers/models (part 1) #53905
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #53905 +/- ##
==========================================
- Coverage 79.61% 79.60% -0.02%
==========================================
Files 4984 4983 -1
Lines 210736 210531 -205
Branches 35877 35846 -31
==========================================
- Hits 167779 167590 -189
+ Misses 37809 37798 -11
+ Partials 5148 5143 -5
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, it took longer then I thought. It seems like one of my change caused openapi-diff issue. My change is probably doing the right thing, however, it will make api schema incompatible. Let me revert the change for that file now, I will see how I can address the issue later. |
Fix mypy errors under src/sentry/api/serializers/models
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.